<!DOCTYPE html>
<html lang="en" class="no-js">
<head>
	<!-- Google Tag Manager -->
		<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
		new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
		j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
		'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
		})(window,document,'script','dataLayer','GTM-WCRD68P');</script>
		<!-- End Google Tag Manager -->
	<!-- Basic Page Needs
        ================================================== -->
	<meta charset="utf-8">
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
	<link rel="icon" type="image/png" href="images/favicon.ico">
	<title>Capella Webinars - Upcoming events, and replays of previous events</title>
	<meta name="description"
		content="Transcript overview of Capella webinar : Seamless Integration of Capella with Jira and Confluence.">
	<meta name="keywords" content="webinars, replay, slides, videos">
	<meta name="author" content="">
	<!-- Mobile Specific Metas
        ================================================== -->
	<meta name="format-detection" content="telephone=no">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<!-- Template CSS Files
        ================================================== -->
	<!-- Twitter Bootstrs CSS -->
	<link rel="stylesheet" href="css/bootstrap.min.css">
	<!-- animate css -->
	<link rel="stylesheet" href="css/animate.css">
	<link rel="stylesheet" href="css/jquery.fancybox.css">
	<!-- template main css file -->
	<link rel="stylesheet" href="css/main.css">
	<!-- responsive css -->
	<link rel="stylesheet" href="css/responsive.css">
	<link rel="stylesheet" href="css/latofonts.css">
	<link rel="stylesheet" href="css/flag-icons.min.css">
	<!-- Cookie content -->
	<link rel="stylesheet" type="text/css"
		href="//www.eclipse.org/eclipse.org-common/themes/solstice/public/stylesheets/vendor/cookieconsent/cookieconsent.min.css" />
	<!-- Eclipse Foundation Google Tag Manager -->
	<script>
		(function (w, d, s, l, i) {
			w[l] = w[l] || [];
			w[l].push({
				'gtm.start': new Date().getTime(),
				event: 'gtm.js'
			});
			var f = d.getElementsByTagName(s)[0], j = d.createElement(s), dl = l != 'dataLayer' ? '&l='
				+ l
				: '';
			j.async = true;
			j.src = 'https://www.googletagmanager.com/gtm.js?id=' + i + dl;
			f.parentNode.insertBefore(j, f);
		})(window, document, 'script', 'dataLayer', 'GTM-5WLCZXC');
	</script>
	<!-- End Google Tag Manager -->
	<!-- Template Javascript Files
        ================================================== -->
	<!-- Angular -->
	<base href="/">
	<script src="js/angular-1.7.8.min.js"></script>
	<script src="angular/capella.js"></script>
	<!-- jquery -->
	<script src="js/jquery-3.4.1.min.js"></script>
	<script src="js/helpers.js"></script>
	<script defer src="https://kit.fontawesome.com/16cf99803e.js" crossorigin="anonymous"></script>
</head>
<body ng-app="capella" data-deferred-cloak>
	<!-- Google Tag Manager (noscript) -->
	<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-WCRD68P"
	height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
	<!-- End Google Tag Manager (noscript) -->
	<!--
        ==================================================
        Header Section
        ================================================== -->
	<ng-include src="'angular/blocks/header.html'"></ng-include>
<section>
	<div class="container">
		<div class="row">
			<div class="section-heading">
			</div>
<!--			<p class="text-center wow fadeInDown" data-wow-delay=".6s">New webinars will be scheduled soon.<p>
			<p class="text-center wow fadeInDown" data-wow-delay=".6s"><a href="https://www.linkedin.com/in/capella-mbse-tool/"><i class="fa fa-linkedin-square"></i> Stay tuned!</a></p><br>
			-->

		<div class="row">
				<h1>Webinar Transcript Summary</h2>
				<h2>Seamless Integration of Capella with Jira and Confluence</h2>
				<i class="far fa-calendar-alt" aria-hidden="true"></i> June 2025 | <i class="fa fa-user-alt" aria-hidden="true"></i>&nbsp;Alex Fournié (Obeo) &amp; Robert Baillargeon (SodiusWillert) | EN&nbsp;&nbsp;&nbsp; <button class="tag">collaboration</button> <button class="tag">traceability</button> <button class="tag">change management</button> <button class="tag">documentation</button>
				<p></p>
				<p> <a href="https://youtu.be/Ar9nRAi4IzI">Video <i class="pl-2 fa fa-brands fa-youtube" aria-hidden="true"></i></a>&nbsp; &nbsp; &nbsp; <a href="resources/pdf/webinars/20250626_CapellaWebinar_Slides_Speaker.pdf">Slides <i class="pl-2 fa fa-brands fa-slideshare" aria-hidden="true"></i></a></p>
<h3>Introduction</h3>
<p>In complex engineering projects, system architecture must become the central reference for all stakeholders: customers, requirements engineers, software and hardware teams, verification and validation specialists, cybersecurity and safety experts, among others. However, each of these actors has different perspectives, needs, and expectations. As a result, the architecture often becomes too complex to be fully understood or effectively used by everyone involved.</p>
<p>One key challenge is integrating the system architecture smoothly into the project lifecycle. Teams must manage change requests, milestones, and various workflows, but architecture models are too often treated as peripheral artifacts, poorly aligned with project governance. With Capella in particular, it remains difficult to embed architecture work in a seamless, project-wide process.</p>

<h3>Key Challenges</h3>
<p>Several important challenges must be addressed to place architecture at the heart of systems engineering:</p>
<ul>
  <li><strong>Smooth Toolchain Integration:</strong> Capella models need to connect easily with the broader systems engineering toolchain, including ALM platforms.</li>
  <li><strong>Traceability:</strong> It must be easy to trace change requests to specific architectural elements.</li>
  <li><strong>Wider Accessibility:</strong> While system architects are familiar with Capella, other stakeholders are not. Architecture models must therefore become more accessible to non-experts.</li>
  <li><strong>Data Consistency and Trust:</strong> If architecture data is outdated or inconsistent, stakeholders will lose trust and revert to working in silos. Breaking down these silos is essential to foster a truly model-based approach to systems engineering.</li>
</ul>

<h3>Proposed Solution</h3>
<p>The solution leverages <strong>Publication for Capella</strong> and <strong>OSLC connectors</strong>, enabling Capella models to be published on a web server. This makes architecture elements accessible via a simple web interface, with no need for specific Capella installations.</p>
<p>The web interface includes a hierarchical view, detailed semantic information, and OSLC links for easy navigation. These links connect Capella to ALM tools like requirements management systems, issue trackers, and change request platforms. They ensure <strong>bidirectional traceability</strong> and integration across Capella, the web publication, and external tools.</p>
<p>Key integrations include:</p>
<ul>
  <li><strong>Confluence:</strong> Using the Sodius/Willert add-on, Capella diagrams and elements can be embedded in Confluence pages. This approach avoids the need for scripts or manual file sharing, while ensuring that information stays <strong>synchronized and up to date</strong> thanks to OSLC.</li>
  <li><strong>Jira:</strong> Capella and Jira are fully interconnected, enabling traceability between model elements and Jira issues. Teams can navigate between the tools and generate traceability reports, supporting rigorous processes, especially in safety-critical systems.</li>
</ul>

<h3>Live Demonstration</h3>
<p>The webinar featured a demonstration of how to model a new <strong>"Welcome Music"</strong> function in the In-Flight Entertainment System using Capella, and manage the associated change process across tools:</p>
<ol>
  <li>An <strong>Epic</strong> and related tasks were created in Jira.</li>
  <li>Requirements, system architecture updates, and documentation were managed collaboratively using Jira and Confluence.</li>
  <li>Capella elements and diagrams were embedded into Confluence via the OSLC Connect macro, enabling <strong>live previews and direct access</strong> to model content.</li>
  <li>The new function was modeled in Capella (including codec definitions such as WMA and AAC) and linked back to the Jira issue.</li>
  <li>Additional changes, such as codec updates, were captured via new Jira tasks created <strong>directly from Capella</strong>.</li>
  <li>The updated model was published online, with all changes automatically reflected in Confluence, with no manual refresh required.</li>
</ol>
<p>This demonstration showcased <strong>real-time synchronization, seamless navigation</strong>, and full traceability between tools using OSLC.</p>

<h3>Roadmap</h3>
<p>Future development priorities for <strong>Publication for Capella</strong> include:</p>
<ul>
  <li><strong>Enhanced version control:</strong> Support for branches, baselines, and historical comparisons directly within the web interface.</li>
  <li><strong>Global configuration:</strong> Improved compatibility with IBM’s global configuration to manage model variants.</li>
  <li><strong>Model reviews:</strong> Online model discussions, reviews, and approval workflows.</li>
</ul>
<p>The roadmap is <strong>customer-driven</strong> and subject to change depending on funding and priorities. Similar improvements are planned for Jira and Confluence integrations, including drag-and-drop support and automation flows across tools using OSLC.</p>

<h3>Q&A Highlights</h3>
<ul>
  <li><strong>Q: Are both cloud and data center versions of Jira and Confluence supported?</strong><br>
  A: Currently, Jira Data Center is supported. Jira Cloud has a different architecture and is not yet supported, but this is a high priority on the roadmap.</li>

  <li><strong>Q: Is Publication for Capella required to publish information into Jira and Confluence?</strong><br>
  A: Yes. Without it, only manual, static copy-pasting is possible. Dynamic publishing and synchronization require Publication for Capella.</li>

  <li><strong>Q: Are there limitations on the number or types of Capella elements that can be linked to Jira or Confluence?</strong><br>
  A: No. All Capella element types can be associated, and there are no limitations on volume. Performance is optimized to load only visible elements.</li>

  <li><strong>Q: Is integration possible between Capella and Jama?</strong><br>
  A: Not currently. Jama does not yet support OSLC, but discussions are ongoing. Interested users are encouraged to contact Jama to express demand.</li>

  <li><strong>Q: Is OSLC Connect available for Polarion?</strong><br>
  A: Yes. Polarion has native OSLC support, unlike Jira and Confluence. No additional plug-ins are needed.</li>

  <li><strong>Q: Does the integration support versioning?</strong><br>
  A: Yes, versioning is supported. OSLC links point to specific configurations or versions. While Capella currently displays the latest version by default, improvements are underway to support full version navigation and comparison.</li>
</ul>
</div>

	</div>
        <div class="row">
        	<div id="webinars_accordion" class="accordion dropdown_content"></div>
			<p class="text-center"><a class="btn btn-default" href="https://www.youtube.com/playlist?list=PLfrEYVpSGVLxEFRODSWUTP8N5i3NTG4o-">Discover all the webinars <i class="fa fa-external-link" aria-hidden="true"></i></a></p>
       </div>
</section>

	<div id="back-to-top" data-spy="affix" data-offset-top="100" class="back-to-top hidden-xs hidden-sm affix-top">
		<button class="btn btn-default" title="Back to Top">
			<i class="fa fa-caret-up"></i>
		</button>
	</div>
	<script type="text/javascript">
		// Back to top
		jQuery('#back-to-top').on('click', function () {
			jQuery("html, body").animate({
				scrollTop: 0
			}, 500);
			return false;
		});
	</script>
	<!--
        ==================================================
        Call To Action Section Start
        ================================================== -->
	<ng-include src="'angular/blocks/call2action_webinars.html'"></ng-include>
	<!--
        ==================================================
        Footer Section
        ================================================== -->
	<ng-include src="'angular/blocks/footer.html'"></ng-include>
		 <!-- bootstrap js -->
        <script defer src="js/bootstrap.min.js"></script>
        <!-- wow js -->
        <script defer src="js/wow.min.js"></script>
        <script defer src="js/jquery.fancybox.js"></script>
        <!-- template main js -->
        <script defer src="js/main.js"></script>
        <!-- Global site tag (gtag.js) - Google Analytics -->
		<script async src="https://www.googletagmanager.com/gtag/js?id=UA-57722280-1"></script>
		<script async src="js/googleAnalytics.js"></script>
        <script async src="//www.eclipse.org/eclipse.org-common/themes/solstice/public/javascript/vendor/cookieconsent/default.min.js"></script>
        <!-- modernizr js -->
        <script defer src="js/vendor/modernizr-2.6.2.min.js"></script>
</body>
</html>
